Method and aerosol delivery device for transmitting aerosol delivery device information

ABSTRACT

A method for an aerosol delivery device may include storing, during use of the aerosol delivery device, information recording usage characteristics of the aerosol delivery device. The method may further comprise creating, using a wireless communication interface of the aerosol delivery device, a connectionless-state advertising packet that includes information relating to an identity and advertising state of the aerosol delivery device and a first set of information recording usage characteristics of the aerosol delivery device from the memory; and transmitting the advertising packet via the wireless communication interface. The method may further comprise receiving a connectionless-state request packet from a remote wireless device, via the wireless communication interface; and responsive to receiving the request packet, creating, using the wireless communication interface, a connectionless state response packet that that includes a second set of information recording usage characteristics of the aerosol delivery device from the memory.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 17/452,361, filed Oct. 26, 2021, which is a continuation ofU.S. patent application Ser. No. 16/610,587, filed Nov. 4, 2019, whichis a National Phase entry of PCT Application No. PCT/EP2018/061086,filed May 1, 2018, which claims priority from GB Patent Application No.1707050.9, filed May 3, 2017, each of which is hereby fully incorporatedby reference herein.

BACKGROUND

The present disclosure relates to data communication and in particularbut not exclusively to a method and apparatus for communication from anaerosol delivery device using connectionless communication link packets.

In the use of aerosol delivery devices such as electronic nicotinedelivery devices (sometimes known as e-cigarettes), there can beinformation gathered by the device relating to the status of thatdevice. This information may be information that is useful to a user ofan aerosol delivery device such as an electronic nicotine delivery(“END”) device in relation to information such as battery charge levelor information relating to remaining nicotine source level such as apuff count and/or total puff duration value. In addition informationsuch as error codes may be generated by the device. Further, there maybe information useful to a user aiming to regulate his or her relianceupon nicotine. Such information may also be of use to some form ofadministrator entity, for example allowing logging of numbers and typesof error occurrences. The inventors have devised approaches foraccessing such information in an energy-efficient and non-intrusivemanner.

Methods of transferring data using low power communications protocolssuch as Bluetooth™ or Bluetooth Low Energy (BTLE), also known asBluetooth Smart, often involve establishing a partnership, bonding,pairing or other connection-based channel between two entities tofacilitate transmitting information over that protocol.

US 2016/0184635 describes a method and apparatus for transmitting andreceiving data using Bluetooth.

US 2013/0065584 describes low energy beacon encoding.

TW201513524A describes monitoring system of physiological informationfollowing Bluetooth low energy protocol.

US 2015/0319555 describes method and apparatus for Bluetooth-based Wi-Fisynchronization.

US 2015/0172391 describes method, apparatus and computer program productfor network discovery.

US 2016/0029149 describes lower power consumption short range wirelesscommunication system.

WO 2016/037012A describes measuring health and fitness data usingproximity sensors and mobile technologies.

US 2016/0021488 describes range management with Bluetooth low energy.

US 2015/0312858 describes method and apparatus for generating aBluetooth low energy data packet comprising audio payload.

US 2016/0037566 describes method and system for optimized Bluetooth lowenergy communications.

US 2011/0021142 describes method and system for a dual-mode Bluetoothlow energy device.

US 2013/0178160 describes systems for facilitating wirelesscommunication and related methods.

WO 2016/108646A describes method and apparatus for controlling deviceusing Bluetooth LE technique.

WO 2016/017909A describes method and apparatus for controllingelectronic device in wireless communication system supporting Bluetoothcommunication.

CN104664605A describes intelligent electronic cigarette with wirelessBluetooth low-power-consumption communication function.

SUMMARY

Particular aspects and embodiments are set out in the appendedindependent and dependent claims.

Viewed from one perspective, there can be provided a method andapparatus for communication from an electronic nicotine delivery deviceusing a connectionless communication link packets.

In a particular approach, there can be provided a method for an aerosoldelivery device. The method can comprise storing, during use of theaerosol delivery device and in a memory of the aerosol delivery device,information recording usage characteristics of the aerosol deliverydevice. The method can also comprise creating, using a wirelesscommunication interface of the aerosol delivery device, aconnectionless-state advertising packet that includes informationrelating to an identity and advertising state of the aerosol deliverydevice and a first set of information recording usage characteristics ofthe aerosol delivery device from the memory; and transmitting theadvertising packet via the wireless communication interface. The methodcan further comprise: receiving a connectionless-state request packetfrom a remote wireless device, via the wireless communication interface;and responsive to receiving the request packet, creating, using thewireless communication interface, a connectionless state response packetthat that includes a second set of information recording usagecharacteristics of the aerosol delivery device from the memory. Therebyan aerosol delivery device may be provided such as to be operable tointeract with a data gathering or logging entity so as to enable usageinformation to be gathered and used, for example, for proactive and/orpredictive interaction with the device or user where issues may haveoccurred or be expected to occur. Other analytics purposes are alsopossible.

In some example, the aerosol delivery device is an electronic nicotinedelivery device. Thereby an electronic nicotine delivery device and usermay benefit from the techniques described herein.

In some examples, the wireless communication interface utilizes anIEEE802.11 or IEEE802.15-derived wireless communication protocol. In oneexample, the wireless communication interface is a Bluetooth or BTLEinterface. Thereby the approach can make use of standardizedcommunications interfaces and modules to provide the techniquesdescribed herein using commonly-deployed communications technologies.

In some examples, the connectionless state advertising packet comprisesa payload which includes the first set of information recording usagecharacteristics, wherein the first set of information recording usagecharacteristics comprises one or more values selected from the groupcomprising: battery properties, aerosol generation properties, aerosolmedium properties, aerosol generation event properties, and erroneous orabnormal behavior properties. Thereby the present approach may be usedto base data logging, reporting and/or predictive activity on specificmeasurable and indicative properties of the particular aerosol deliverydevice.

In some examples, the connectionless state response packet comprises apayload which includes the second set of information recording usagecharacteristics, wherein the second set of information recording usagecharacteristics comprises one or more values selected from the groupcomprising: battery properties, aerosol generation properties, aerosolmedium properties, aerosol generation event properties, and erroneous orabnormal behavior properties. Thereby the present approach may be usedto base data logging, reporting and/or predictive activity on specificmeasurable and indicative properties of the particular aerosol deliverydevice.

In some examples, the connectionless state response packet furtherincludes information relating to an identity of the aerosol deliverydevice. Thereby, the logging, reporting and/or predictive activity canbe individualized to a particular device.

In some examples, at least one of the first set of information recordingusage characteristics and the second set of information recording usagecharacteristics are arranged in the payload according to a predeterminedschema defining the order and size of the values included in thepayload. Thereby, the present approach may be able to communicate in astandardized way that facilitates efficient data communication withminimal overhead.

In another particular approach, there can be provided an aerosoldelivery device, comprising: a memory configured to store, during use ofthe aerosol delivery device, information recording usage characteristicsof the aerosol delivery device; and a wireless communication interfaceconfigured to transmit, a connectionless-state advertising packet thatincludes information relating to an identity and advertising state ofthe aerosol delivery device and a first set of information recordingusage characteristics of the aerosol delivery device from the memory.The wireless communication interface can be further configured toreceive a connectionless-state request packet from a remote wirelessdevice; and to transmit a connectionless state response packet that thatincludes a second set of information recording usage characteristics ofthe aerosol delivery device from the memory. Thereby an aerosol deliverydevice may be provided such as to be operable to interact with a datagathering or logging entity so as to enable usage information to begathered and used, for example, for proactive and/or predictiveinteraction with the device or user where issues may have occurred or beexpected to occur. Other analytics purposes are also possible.

Such a device can include elements or configuration to enable it toperform in accordance with the various method examples outlined above.

In a further particular approach, there can be provided a systemcomprising: the aerosol delivery device outlined above; and a remotewireless device. The remote wireless device can comprise: a wirelesscommunication interface configured to receive the connectionless-stateadvertising packet from the aerosol delivery device, to transmit theconnectionless-state request packet, and to receive the connectionlessstate response packet.

BRIEF DESCRIPTION OF FIGURES

Embodiments of the present teachings will now be described, by way ofexample only, with reference to accompanying drawings.

FIG. 1 schematically illustrates an advertising protocol.

FIG. 2 schematically illustrates an example devices environment.

FIG. 3 schematically illustrates messages between devices.

FIG. 4 schematically illustrates a message.

FIG. 5 schematically illustrates a message payload.

FIG. 6a schematically illustrates a first message schema.

FIG. 6b schematically illustrates a second message schema.

FIG. 7 schematically illustrates an aerosol delivery device.

FIG. 8 schematically illustrates a logging device.

While the presently described approach is susceptible to variousmodifications and alternative forms, specific embodiments are shown byway of example in the drawings and are herein described in detail. Itshould be understood, however, that drawings and detailed descriptionthereto are not intended to limit the scope to the particular formdisclosed, but on the contrary, the scope is to cover all modifications,equivalents and alternatives falling within the spirit and scope asdefined by the appended claims.

DETAILED DESCRIPTION

The present disclosure relates to a modified form of wirelesscommunication behavior. According to the present teachings, a device canbe configured to use a BTLE or BTLE-like communications protocol toachieve connectionless sharing of information relating to END devicestatus and/or usage.

In the present examples, the aerosol delivery devices use BTLE, butother Bluetooth protocols or Bluetooth-like protocols can take advantageof the present teachings. Bluetooth is a wireless technology standardfor short distance communication between appropriately enabled devices.BTLE is a variant on the original Bluetooth system, designed to drawless power in use for extended battery life and/or small batteryapplications. Both Bluetooth and BTLE operate in the UHF radioindustrial, scientific and medical (ISM) band from 2.4 to 2.485 GHz andare designed for creating so-called wireless personal area networks(PANs) for interconnecting devices over short distances. BTLE uses amodified version of the Bluetooth stack for communication such that aBTLE device and a traditional Bluetooth device are not directlycompatible unless one device implements both protocols. Both Bluetoothand BTLE standards are maintained by the Bluetooth Special InterestGroup (SIG). The present disclosure is provided in the context of a BTLEimplementation using the part of the Bluetooth v4 specification thatrelates to BTLE. However, the skilled reader will appreciate that thepresent teachings can be applied to other Bluetooth approaches, such asthe so-called Classic Bluetooth definitions that are also set out in theBluetooth v4 specification. It will be further appreciated that thepresent teachings can be applied to technologies that are not inaccordance with an entire Bluetooth specification, but whichnevertheless behave in a Bluetooth-like manner.

For example, non-Bluetooth systems that nevertheless use an advertisingsetup based on the BTLE Generic Access Profile (GAP) and thus have anadvertising structure substantially as set out in FIG. 1 would be ableto deploy the techniques of the present teachings. FIG. 1 illustrates anadvertising structure according to which a peripheral (or slave orremote or secondary) device advertises its availability as a peripheral(or slave or remote or secondary) device during an advertisement period,with the advertisement periods being separated by an advertisementinterval. The advertisement may include data for transmission, anindication that there is data for transmission or have no data referenceat all. To receive the advertisement, a central (or primary or control)device scans for advertisements during a scan window. Multiple scanwindows are separated by a scan interval. The relative duration of thescan and advertisement intervals is altered, either by determining thatthe interval at one device type is constant while the other varies, orby determining that both vary, which determination can be set by astandard or rule set for implementing the advertising protocol. Byproviding this relative variation in the scan and advertisementintervals, it is provided that even where an initial advertisementperiod does not overlap with an initial scan window, after a number ofadvertisement and scan intervals, an advertisement period will occurwhich overlaps with a scan window such that a connection can beinitiated between the central and the peripheral device.

A first example of a devices environment 10 in which the presentteachings can be utilized is shown in FIG. 2. In this example, anaerosol delivery device 12 is operable to communicate with a loggingdevice 16 via a communication channel 14. Further, in some examples, thelogging device 16 may be operable to communicate via a communicationchannel 18 with a remote network service 20.

As discussed above, the aerosol delivery device 12 may be and ENDdevice. The logging device 16 may be any suitable device havingcompatibility with the wireless communication channel 14. As illustratedin FIG. 2, the logging device 16 may for example comprise one or more ofa communication access station, such as a base station or similar devicefor the wireless communication channel 14. The logging device 16 mayalso or alternatively comprise a computing device such as a tabletcomputer, smartphone, portable computer, desktop computer, server orother multipurpose computing device including or attached to aninterface for the wireless communication channel 14.

In the present example, the wireless communication channel 14 is a BTLEor BTLE-like channel which transfers data packets between the aerosoldelivery device 12 and the logging device 16 using a connectionlessstate of a communication protocol or a connectionless communicationprotocol.

The communication channel 18 between the logging device 16 and theremote network service 20 may be a wired and/or wireless channel and mayuse the same or different network protocols as the wirelesscommunication channel 14. In the present examples, the communicationchannel 18 may be a conventional network data connection such as a WI-FI(IEEE802.11x) or Ethernet-based connection, for example usingconventional network transport and data protocols such as TCP/IP,Fiberchannel and Infiniband.

The remote network service 20 may be accessed via a public or privatenetwork such as a WAN or the Internet. The remote network service 20 maybe provided on dedicated or shared network resources as a public orprivate cloud service.

Using the structure illustrated in FIG. 2, the aerosol delivery device12 may provide various usage and/or status data about that device to oneor more logging devices 16 using a connectionless transmissionarrangement, i.e. without a formal bonding, pairing or other connectionestablishment process. This may facilitate straightforward andnon-intrusive collection of data from the aerosol delivery device 12.Therefore, the aerosol delivery device can be enabled to automaticallycollect and collate usage/status data and then provide this to thelogging device, which can identify and extract the data from the aerosoldelivery device and if necessary process this data into an informationformat for use in logging and/or analyzing the data. The data from theaerosol delivery device may be further forwarded/uploaded to the remotenetwork service for centralized handling of the information conveyed bythe data.

An approach for sending and receiving data packets between the elementsillustrated un FIG. 2 is shown in FIG. 3. In FIG. 3, it is illustratedthat the aerosol delivery device 12 sends out an advertising packet,identified as ADV_IND in FIG. 3 (in BTLE terminology, a device listeningfor advertising packets is termed a “peripheral” device). The ADV_INDpacket is not directed to a particular other device, but can be receivedand read by any device within transmission range that is listening foradvertising packets (in BTLE terminology, a device listening foradvertising packets is termed a “central” device). This packet providesadvertising function for the sending device, setting out sufficientidentity details of the sending device that a receiving device canconstruct a response packet that identifies the sending device in suchmanner that the sending device will understand that it is the intendedrecipient of the response packet. The ADV_IND packet may also beconnectable, in the sense that it can be used as the first stage in aprocess of establishing a connection (such as a bonding or pairingconnection) between the sending device and a receiving device. In thepresent example however, such connectable capability is not utilized toachieve the transmission of the aerosol delivery device status/usagedata.

The logging device 16, upon receipt of the ADV_IND packet from theaerosol delivery device 12 uses the identification information from theADV_IND packet to send a reply to the aerosol delivery device 12 in theform of a request packet, identified as SCAN_REQ in FIG. 3. This packetrequests further information from aerosol delivery device.

When the aerosol delivery device 12 receives the SCAN_REQ packet, itthen generates and transmits a response packet, identified as SCAN_RSPin FIG. 3, directed to the logging device 16. From the point of view ofthe aerosol delivery device 12, the logging device 16 may be consideredas a remote wireless device, as the aerosol delivery device 12 may beagnostic as to the exact nature of any other device with which itexchanges advertising packets. Optionally, there may be an onwardtransmission by the logging device 16 of the status/usage data receivedthe aerosol delivery device. This onward transmission may be directed toa remote network service 20 and is illustrated as [upload] in FIG. 3.

Once the SCAN_RSP packet is received by the logging device 14, theexchange of packets between the aerosol deliver device 12 and thelogging device 16 is complete. It is possible for this process to becomplete at this time as the present techniques actually provide theaerosol delivery device usage/status data within the ADV_IND andSCAN_RSP packets.

In the present example, each of the ADV_IND and SCAN_RSP packets has apacket structure that includes space for payload information. Thispayload information space is used by the present techniques to conveythe aerosol delivery device usage/status data. Detailed examples ofpacket structures will now be described with reference to the BTLEpackets, although it will be appreciated that another transmissionprotocol or stack that provides for a similar advertising packetsequence with the capability for payload in the advertising and responsepackets can also be used to achieve the results of the presentteachings.

The packet structure used by the ADV_IND and SCAN_RSP packets discussedwith respect to FIG. 3 above includes a preamble, an access address, apacket data unit and an error check code. A typical example structure isshown in FIG. 4. According to the usual BTLE packet structures, thepreamble has a size of 1 byte and is used for internal protocolmanagement. The Access Address has a size of 4 bytes and is set to afixed predetermined value for advertising packets. The Packet Data Unit(PDU) is a payload space that can be used to carry additionalinformation, and has a size in the range of 2 to 39 bytes. The errorcheck code (ECC) is used as an error check coding and typically is basedupon a cyclical redundancy check (CRC) calculated from the other bits ofthe packet.

The structure of the Packet Data Unit is illustrated in FIG. 5. Asshown, there is provided a PDU Header and a Payload. The PDU Header hasa length of 2 bytes and includes details of the packet type (i.e. in thepresent examples the packet type identifiers used are those for ADV_IND,SCAN_REQ, and SCAN_RSP). The header may also include details of thepayload length, as the payload can have variable length.

The actual data payload is then included in the payload, which can havea size of up to 37 bytes. The payload includes the address of thesending device (the aerosol delivery device 12 in the case of ADV_INDand SCAN_RSP packets). This takes up 6 bytes of the maximum payloadsize. The payload may also include a destination address whereapplicable (e.g. in SCAN_RSP the address of the logging device 16 thatsent the SCAN_REQ), this also is expected to take up 6 bytes of themaximum payload size.

The remaining bytes of payload space (a maximum of 31 bytes as the other6 bytes of the maximum PDU size are used for the address of the sendingdevice) in an ADV_IND packet may typically be used to may containadvertising data from the advertiser's host, such as advertisingservices and a convenient device name. In the present approaches, theremaining payload space is, instead of advertising data about theadvertiser, controlled to carry data gathered from the device in use,which data describe the aerosol delivery device usage and/or status.Thus this usage/status information may be conveyed without the need toestablish a formal connection (such as a pairing or bonding connection)between the aerosol delivery device and the logging device. The payloadof both the ADV_IND and SCAN_RSP can be controlled in this way.

Various examples of data fields about an aerosol delivery device 12 suchas an END device that may have utility in managing or receivingreporting from the aerosol delivery device 12 by the logging device 16and/or a remote network service 20 are now set out:

Puff Count (the number of aerosol delivery operations carried out by thedevice, definable as total operations for the device or operations sincea change event such as a new aerosol content cartridge being inserted)

Puff Duration (the average duration or total summed duration of aerosoldelivery operations, typically over the same duration as the Puff Count)

Battery Charges (the number of battery charge/discharge cycles carriedout on the device)

Average Battery percentage before charge (an indication of the averagepercentage charge value at the time that a charge is commenced)

Overheat Protection (the number of times that overheat protectionfunction has been engaged in the device)

Error Codes (any error codes currently indicated by the device and/or anoccurrence history of error codes in the device) Puff too Short (anindication of aerosol delivery operations that fall below a thresholdduration to ensure that aerosol content is actually delivered)

Cartomizer Used (an indication of an aerosol content cartridge currentlyinstalled in the device)

Puffs per power profile (a count of aerosol delivery operations for eachof a number of different power profiles, for example high, medium andlow)

Current Power Settings (an indication of current power settings aspresently set for use in a next aerosol delivery operation)

Charged duration (an indication of the length of time for which thedevice has held sufficient charge for aerosol delivery operations)

Battery Threshold before charge (an indication of remaining batterycharge, expressed as a percentage, hours of standby, and/or number ofaerosol delivery operations at present power settings, etc.)

Boot/Uptime Time(s) (an indication of a number of power-on cycles and/ora duration of power on status)

Product Type (an identifier of a product type of the device)

Batch Number (an identifier of a batch number of the device)

Serial Number (an identifier of a serial number of the device)

Duration of Device On time (an indication of a duration of power onstatus)

Duration of Device Off time (an indication of a duration of power offstatus)

Device/Coil temperature (an indication of a current and/or history ofthe device temperature and/or a temperature of a heater coil used foraerosol generation)

As will be appreciated, a wide variety of such fields relating to thecurrent and historical usage/status of the device may be created andused depending on the requirements of the aerosol delivery device,logging device and/or remote network service. For example, in anarrangement where an application provided at the logging device and/orremote network service is concerned with successful operation of thedevice and providing error feedback to a user or administrator, thenfields relating to error codes, physical status (temperature, battery,uptime etc) and device identity (product, batch, serial, etc.) may beemphasized. In an arrangement where an application provided at thelogging device and/or remote network service is concerned with analyzingusage statistics, then fields relating to aerosol delivery activity(puff count, puff duration, puffs per power, charge duration etc) may beemphasized. However, in order to enable applications with a range ofcontent interests and emphases to operate successfully with the aerosoldelivery device without introducing a requirement for detailed datarequests of a type that might encourage or require a connection to beestablished with the aerosol delivery device, the aerosol deliverydevice may be preconfigured (for example at manufacture, sale orpost-sale by a user interface provided by an application that doesconnect using a connection-based exchange of setting information withthe device) to provide any or all possible data fields when advertisingusing ADV_IND packets and when replying to a SCAN_REQ packet with aSCAN_RSP packet.

Thus the present teaching also provides for such fields to betransmitted within the combination of the ADV_IND and SCAN_RSP packets.Examples of one possible schema for including fields for the devicestatus/usage in the payload of ADV_IND and SCAN_RSP packets isillustrated in FIGS. 6a and 6b . In FIG. 6a , the ADV_IND payloadcontent commences with a UUID (Universally Unique Identifier). Eachdevice subscribing to the communication protocol (BTLE in the presentexamples) has an identifier that identifies that device as beingdistinct from any other. In the present examples (consistent with thedefinition in BTLE) the UUID has a length of 128 bits—this creates amaximum pool of 2¹²⁸ possible unique devices. The payload of the ADV_INDpacket then includes 7 fields of up to 2 bytes each in length. In oneexample, these may be assigned as follows: A—Product/Batch ID, B—PuffCount, C—Error Codes, D—Puffs in high power, E—Puffs in medium power,and G—Puffs in low power.

In FIG. 6a , the SCAN_RSP payload content includes a further 7 fieldswhich are illustrated as having varying lengths. In one example, thesemay be assigned as follows: H—Total Battery Charges, I—Average batterypercentage before charge, J—time since last charge, K—time since lastpower-on cycle, L—puff duration, M—time spent charging, N—total overheatevents. In addition, some space is indicated as reserved (i.e. unused inthis example schema) but which could be used in an alternative schema.

By defining the schema of field delivery within the ADV_IND and SCAN_RSPpackets in advance, the receiving logging device can interpret the datameaning according to the data position within the packet payload. Thispermits high efficiency use of the limited data space within thepackets. The schema may be fixed for the life of the device, or may bemodifiable either by a systems implementer or a user.

It will be appreciated that the present approach involves transmissionof the data from the aerosol delivery device 12 to the logging device16. Therefore, to illustrate suitable devices for providing suchtransmission of data, an example aerosol delivery device and an examplelogging device are illustrated with respect to FIGS. 7 and 8respectively.

An example of an aerosol delivery device 12 is schematically illustratedin FIG. 7. As shown, the aerosol delivery device 12 is a device whichcontains elements relating to aerosol generation such as an aerosolmedium container or cartridge 30 (in the case of an END device, theaerosol medium container or cartridge 30 will contain nicotine or anicotine-bearing formulation), an aerosol generation chamber 31 and anoutlet 32 through which a generated aerosol may be discharged. A battery33 may be provided which to power a thermal generator element (such as aheater coil 34) within the aerosol generation chamber 31. The battery 33may also power a processor/controller 35 which may serve purposes ofdevice usage, such as activation of the device for aerosol generation inresponse to an activation trigger, and purposes of device monitoring andreporting. Processor/controller 35 may have access to a memory 36 inwhich data collected or determined by the processor/controller can bestored pending transmission. The memory 36 may be internal to theprocessor/controller or may be provided as an addition separate physicalelement. To perform transmission of data stored in the memory 35, theprocessor/controller is provided with a transmitter/receiver element 37.In the present example, this is a BTLE interface element including aradio antenna for wireless communication.

As illustrated, processor 35 may be connected for example to aerosolmedium container or cartridge 30, aerosol generation chamber 31 andbattery 33. This connection may be to an interface connection or outputfrom ones of the components and/or may be to a sensor located at or inones of the components. These connections may provide access by theprocessor to properties of the respective components. For example abattery connection may provide an indication of current charge level ofbattery 33. By measuring the battery charge level over time, thecontroller/processor 35 may be able to determine and store values forany or all of data fields such as a current (i.e. most recent) batterylevel, an average minimum charge level reached before a recharge event,low battery conditions, and a total number of recharge events. Asanother example, a connection to aerosol medium container or cartridgemay provide that the controller/processor 35 can determine and storevalues for any or all of data fields such as when a container orcartridge change occurs, an identifier of a currently fitted containeror cartridge, and a current level of remaining aerosol medium. As afurther example, a connection to aerosol generation chamber may providethat the controller/processor 35 can determine and store values for anyor all of data fields including coil overtemperature events, coilactivation events (representative of puff events), coil activationduration (representative of puff duration), etc. In addition, theprocessor/controller 35 can use an internal or external clock to makereference to events over time and thus determine and store data fieldsrelating to measurements over time, and/or to determine and store datafield relating to duration of individual events, and also to comparesuch durations to threshold in order to detect under- or over-durationaerosol generation events. Also, the processor/controller 35 can alreadyknow and store information on the device identifier, serial number etc,and also information on current power level settings to be applied foraerosol generation events. The processor/controller 35 can also be awareof the currently defined data transmission schema such that it canpackage the data into structures for transmission. Thus the aerosoldelivery device 12 of the present examples can determine and store avariety of data relating to current and historical usage of the aerosoldelivery device, and then package that data into a predefined datapayload schema and include such packaged data in advertising messagesand response messages to enable that data to be passed on to the loggingdevice 16.

An example of a logging device 16 is schematically illustrated in FIG.8. As shown, the logging device 16 includes a receiver transmitterelement 40 for receiving advertising and response packets from theaerosol delivery device and for sending request packets to the aerosoldelivery device. In the example where the aerosol delivery device uses aBTLE transmitter/receiver element, the receiver transmitter element 40of the logging device 16 is also a BTLE capable or compatible element.The receiver transmitter element 40 is connected to a processor orcontroller 41 which can receive and process the data received from theaerosol delivery device. The processor or controller 41 has access to amemory 42 which can be used to store program information and/or data.The logging device 16 may be a dedicated logging device arranged with aprincipal purpose of receiving and recording data from aerosol deliverydevices, such as may be referred to as a sniffer device or the like. Insuch an example, any program instructions for the processor orcontroller 41 may be related solely to performing the logging/sniffingfunctionality and any onward forwarding or transmission functionality.Alternatively, the logging device 16 may be a base station or similardevice for the wireless communication channel 14, in which case theprogram instruction may relate to the logging/sniffing functionality anda base station functionality. In further alternatives, the loggingdevice 16 may be a general purpose computing device such as a tabletcomputer, smartphone, portable computer, desktop computer, server orother multipurpose computing device, in which cases the applicationinstructions for the processor or controller 41 may be general purposeoperating system instructions and instructions for other applicationsinstalled to the device, where the logging/sniffing functionality isprovided as an application operable by the device in addition to otherprogrammed functionalities.

The logging device 16 may include a further data transmission interface43. This interface may provide one or more interface functionalities,for example to a wired connection such as Ethernet, Infiniband orFiberchannel and/or to a wireless connection such as Wi-Fi, Bluetooth orZigBee, and or all of which may be compatible with the communicationchannel 18. This interface may be used where a particular implementationrequires the capability for onward transmission of the data receivedfrom the aerosol delivery device 12 to a remote network service 20. Thelogging device may also include user interface elements such as anoutput device 44 (which may include one or more of a display, an audiooutput, and a haptic output) and/or an input device 45 (which mayinclude one or more of buttons, keys, touch-sensitive display elements,or a mouse/trackpad).

The remote network service 20, if implemented, will include an interfacecapable of receiving data over the selected communication channel 18.The remote network service 20 may be include one or more computeresources and one or more storage resources, by use of which the remotenetwork service may process the status/usage data of one or more aerosoldelivery devices to provide reporting and/or control of an aerosoldelivery devices estate. For example, the network service may providecentralised logging of types, frequencies and totals of error codesexperienced by a number of aerosol delivery devices of a number ofdifferent product types and/or batches.

Processing of the data from the aerosol delivery device may be performedat either or both of the logging device 16 and the remote networkservice 20. Such processing may provide user-level and/oradministrator-level information relating to one or more aerosol deliverydevices. Such information can be provided to a user and/or administratorusing a suitable user interface, such as a graphical user interface thatmay be displayed on a display device. User-level information could beused to provide feedback to a user on their personal usage habits,including the likes of how many aerosol generation events that have madeover a given time period and/or at each of a number of power levelsand/or using what aerosol medium. Such information may be of use to auser that is looking to regulate their aerosol medium intake to match(or exceed or not exceed) a personal goal or target of the user. Suchinformation may also provide more information to a user of an aerosolgeneration device about their usage than was previously available.Administrator-level information could be used to provide productquality/reliability reporting by enabling a comparison of differentproducts or batches of the same product against undesirable usagebehavior such as over-temperature conditions or other error indicators.Such information could be fed back into a product design process tooptimize reliability of future devices. Administrator-level informationcould also be used to identify market information or market trends, suchas usage patterns of different aerosol medium containers or cartridgesin aerosol delivery devices sold into different markets.

It is seen from the present examples that information provided by anaerosol delivery device containing the usage/status information may betransmitted in the open (i.e. without specific encryption). However, itis also noted that the information is anonymous in the sense that theonly identifying information (UUID, product identifier, serial number,batch number etc) relates to the device rather than to the user. Also,the schema for data transmission does not require field labels to beincluded in the data packets, such that the packet data can in practicecontain only one or more values for each filed in such a way that to thecasual observer it contains nothing more than a random sequence of databits. Further, as the schema can be in some examples modified as betweenthe user and their device, each user may have a customized schema whichprevents knowledge of a default schema from being able to identify themeaning of the data in the packets. Thus it is seen that transmission ofthe advertising and response packets is in fact secure despite notnecessarily including a specific conventional security technique such asencryption.

It is however possible to implement the system of the present examplesusing encryption of the data is required (for example if the schema weremodified to include data which the user of the aerosol device wished tokeep protected, such as personal identifying data of the user). To doso, the aerosol delivery device and logging device can be caused toestablish a connection which can be used to exchange suitable encryptionkeys for use by the aerosol delivery device when preparing the payloadinformation for the advertising and response packets. Then, even aftersuch connection has been stopped, the aerosol delivery device may usesuch encryption keys to encrypt the data in the payload, while alsoincluding in the payload an identifier (in the manner of a session keyor similar) which identifies to the receiving logging device details ofthe encryption used so that the logging device can use the correctdecryption key to access the transmitted data.

Thus there has been described a complete solution for gathering andproviding aerosol delivery device status and/or usage information to alogging device through a connectionless exchange of data packets inwhich the information is passed using advertising and response packetssent from the aerosol delivery device.

It has been described above, that the technology used to implement thepassing of data packets in a connectionless manner is achieved usingBTLE ADV_IND and SCAN_RSP packets in a BTLE communications environment.It is also possible to use alternative technologies to achieve asimilarly connectionless transfer of the aerosol delivery deviceusage/status data. As will be appreciated, BTLE is a subset of theBluetooth specifications, which were originally defined within theIEEE802.15 framework. Other IEEE802.15 compliant or derived technologies(sometime references as personal area network or PAN technologies) suchas (non-BTLE) Bluetooth (including Bluetooth 5, which no longer uses the“LE” designation), Zigbee or Z-Wave could be used to provide theconnectionless transfer of the usage/status data. In addition, otherwireless technologies such as Wi-FI (IEEE802.11n) or similar could beused to provide the connectionless transfer of the usage/status data.

As will be appreciated from the above discussion, both the aerosoldelivery device 12 and the logging device 16 may be required to storedata relating to the various usage/status fields in a memory of therespective device. On one implementation, this is performed by defininga static framework structure for memory usage in which particular fieldvalues are stored at particular predefined memory locations or atparticular predefined locations within a data file format. Such astructure may also include a label or identifier for each field withinthe framework structure. In alternative implementations, either or bothof the storage at the aerosol delivery device 12 and the logging device16 may be arranged to store the data according to a dynamic allocationstructure. This would avoid memory space being used for specific fieldsthat are unused at any given point in time, but would require that thelabel or identifier for each field is used within the dynamic memorystructure.

Therefore, the present teachings have provided an approach for gatheringand providing data corresponding to a number of metrics representativeof the usage or status of an aerosol delivery device. This is achievedwithout a need for device pairing or connection such that a user neednot provide pre-configuration or ongoing interaction with the aerosoldelivery device. The use of connectionless data transfer further avoidsa need for user pre-configuration or ongoing interaction with theaerosol delivery device. At the same time, user configuration can beprovided in specific implementations if appropriate.

The various embodiments described herein are presented only to assist inunderstanding and teaching the claimed features. These embodiments areprovided as a representative sample of embodiments only, and are notexhaustive and/or exclusive. It is to be understood that advantages,embodiments, examples, functions, features, structures, and/or otheraspects described herein are not to be considered limitations on thedisclosure scope defined by the claims or limitations on equivalents tothe claims, and that other embodiments may be utilized and modificationsmay be made without departing from the scope and/or spirit of theclaims.

1. A method for an aerosol delivery device, the method comprising:creating, using a wireless communication interface of the aerosoldelivery device, a connectionless-state advertising packet, wherein theadvertising packet is configured to provide information which is to beused by a remote wireless device to construct a response packet in sucha manner that the aerosol delivery device will understand that it is theintended recipient of the response packet; transmitting the advertisingpacket to the remote wireless device, via the wireless communicationinterface; using, at the remote wireless device, the information fromthe advertising packet to send a response packet to the aerosol deliverydevice in the form of a connectionless-state request packet, wherein theconnectionless-state request packet is constructed in such a manner thatthe aerosol delivery device will understand that it is the intendedrecipient of the connectionless-state request packet; and receiving, atthe aerosol delivery device, the connectionless-state request packetfrom the remote wireless device, via the wireless communicationinterface of the aerosol delivery device.
 2. The method of claim 1,wherein the connectionless-state advertising packet further comprisesstatus data about the aerosol delivery device, wherein the methodfurther comprises: the remote wireless device, after receiving theadvertising packet, extracting the status data from the advertisingpacket.
 3. The method of claim 2, wherein the method further comprisesthe remote wireless device: uploading the status data to a remotenetwork service.
 4. The method of claim 1, wherein the method furthercomprises the remote wireless device uploading an onward transmission toa remote network service at a time after the remote wireless device hasreceived the advertising packet from the aerosol delivery device.
 5. Themethod of claim 1, wherein the aerosol delivery device is an electronicnicotine delivery device.
 6. The method of claim 1, wherein the wirelesscommunication interface utilises an IEEE802.11 or IEEE802.15-derivedwireless communication protocol.
 7. The method of claim 1, wherein thewireless communication interface is a Bluetooth or BTLE interface. 8.The method of claim 1, wherein the connectionless state advertisingpacket includes information relating to an identify of the deliverydevice.
 9. The method of claim 1, wherein the connectionless stateadvertising packet comprises a payload which includes the information.10. The method according to claim 1, wherein the method comprises:storing, during use of the aerosol delivery device and in a memory ofthe aerosol delivery device, information recording usage characteristicsof the aerosol delivery device.
 11. The method according to claim 1,wherein the remote wireless device comprises a smartphone.
 12. Anaerosol delivery device, comprising: a wireless communication interfaceconfigured to transmit, to a remote wireless device, aconnectionless-state advertising packet, wherein the advertising packetis configured to provide information which is to be used by a remotewireless device to construct a response packet in such a manner that theaerosol delivery device will understand that it is the intendedrecipient of the response packet; the wireless communication interfacefurther configured to receive a response packet in the form of aconnectionless-state request packet from the remote wireless device,wherein the aerosol delivery device is configured to understand that itis the intended recipient of the response packet.
 13. The device ofclaim 12, wherein the aerosol delivery device is an electronic nicotinedelivery device.
 14. The device of claim 12, wherein the wirelesscommunication interface utilises an IEEE802.11 or IEEE802.15-derivedwireless communication protocol.
 15. The device of claim 12, wherein thewireless communication interface is a Bluetooth or BTLE interface. 16.The device of claim 12, wherein the connectionless state advertisingpacket comprises a payload which includes the information.
 17. Thedevice of claim 12, wherein the connectionless-state advertising packetfurther comprises status data about the aerosol delivery device.
 18. Thedevice of claim 12, wherein the connectionless-state advertising packetfurther comprises a payload which includes identity information andstatus data about the aerosol delivery device.
 19. A system comprising:the aerosol delivery device of claim 12; and a remote wireless devicecomprising: a wireless communication interface configured to: receivethe connectionless-state advertising packet from the aerosol deliverydevice; and transmit the connectionless-state request packet back to theaerosol delivery device.